COMMENT ⊗   VALID 00007 PAGES
C REC  PAGE   DESCRIPTION
C00001 00001
C00002 00002	Introduction
C00003 00003	Use of DM Hardware
C00006 00004	Use of DM Software
C00020 00005	Use of DMs via TIPs
C00024 00006	Use of DMs from TENEX/TOPS20 Hosts
C00026 00007	Use of DMs from ITS Hosts
C00029 ENDMK
C⊗;
Introduction


This file, DM.ME[UP,DOC], lists some  facts and procedures of interest  to
users of the Datamedia  Elite 2500A display  terminal equipped with  SUMEX
keyboard (hereafter abbreviated "DM"), and other terminals (e.g.,  IMLACs)
which emulate DMs.
Use of DM Hardware


When using terminal with 300 baud modem:

(1) Connect pins 2, 3, and 7 of the DM LINE connector to pins 2, 3, and 7,
respectively, of the modem's TERMINAL connector.

(2) Switch the terminal's speed selector to 300, and dial in.

(3) To disconnect, hang up the phone.


When using terminal with internal 1200/150 modem:

(1) Connect stub cable coming out of back of terminal into the  terminal's
LINE connector.

(2) Plug white cable into jack at back of terminal.

(3) If your phone doesn't have a jack, remove the cover of the little  box
where the wire goes into the  wall and replace with the adapter  provided,
creating a phone jack.

(4) Plug other end of white cable into your phone jack.

(5) If the phone has a  plug, plug it into the  back of the plug you  just
inserted.

(6) Switch the terminal's speed selector to SEL.

(7) Push the small switch next to the speed selector to the left.

(8) Now dial SU-AI or AMES-TIP (or whatever).  When the modem answers with
a tone, switch the small switch to the right and hang up the phone.

(9) To disconnect, push the  BREAK key on the  terminal for a few  seconds
until the CD light (the top one in the column of lights below the  screen)
goes out, and then push the small switch to the left and the line will  be
released.  PLEASE don't forget to  hit BREAK before disconnecting; if  you
forget, the modem you were  talking to at the  computer end may think  you
are still there (forever).
Use of DM Software


[Note:  If you have trouble with  typeout at any time, especially if  tabs
in the typeout don't seem  to work, type [BREAK] P  (see below for how  to
type this), which will  clear and refresh  your screen, including  setting
your DM's tab stops.  If your DM doesn't have tab stops, type the  monitor
command TTY NO TABS  and then type  [BREAK] P.  If  you have trouble  with
your line editor, type [ESC] R.]

DM terminals are considered full display  terminals by the system, and  as
such they have  virtually all  the capabilities  possessed by  DD and  III
displays except (1) keyboard and screen mapping, (2) audio switch control,
and (3) vector displaying.  In  particular, the line editor, the  wholine,
and the full Stanford AI Lab character set with CONTROL and META bits  are
available on DMs, although a few  Stanford characters must be quoted  (see
below) in order to be input.

To have a list of DM keyboard commands printed on the XGP, type HELP DMKEY
to the monitor and follow instructions; this  can only be done on a DD  or
III display  since  it  causes  XGP  output  which  should  be  picked  up
immediately.

Since the  DM  keyboard  does  not  have keys  for  all  of  the  Stanford
characters, certain characters must be typed in their ASCII CTRL form; for
example, partial-sign (∂) is ↑O and  thus must be input as CTRL-O.   Also,
since  the  DM  display  does  not  have  symbols  for  all  the  Stanford
characters, those characters that must be typed in as CTRL-something  will
be displayed in  a special  form, namely  as either  BOLD-something or  as
BLINKING-something.   On  SU-AI   DMs,  CTRL-something   will  appear   as
BOLD-something; on other DMs  that have not  been modified to  interchange
the  BLINKING   and  BOLD   functions,  CTRL-something   will  appear   as
BLINKING-something.  For example, on SU-AI DMs partial-sign (∂ or ↑O) will
be displayed as BOLD-o; on non-modified DMs it will be BLINKING-o.  If you
have a non-modified DM and don't like blinking (you won't), then type  TTY
NO BOLD or use  the NOBOLD LOGIN  option.  The XGP  printout made by  HELP
DMKEY lists the  correspondences between  Stanford AI  Lab characters  and
their ASCII CTRL representation.

Here is a summary of what you have to type to get certain effects:

	To get [ESC], type [NUL].  Most DD-type ESC commands work on DMs.
	To get [BREAK], type [NUL] and then "-" (minus sign).
	To get (CONTROL)<char>, type (EDIT)<char>; that is, hold down
		(EDIT) while typing <char>.
	To get (META)<char>, type (EDIT)[NUL] and then <char>.
	To get (META)(CONTROL)<char>, type (EDIT)[NUL] and then
		(EDIT)<char>.

	To undo [ESC] or [BREAK], type [DEL].
	To undo (META), type [NUL] and then [DEL].

	To get [CLEAR], type the bottom unlabelled key at keyboard left,
		or [MR].
	To get [FORM], type [↑L].
	To get [BS], type [DEL].
	To get [CALL] (that is, two ↑C's), type [CALL].
	To get deferred [CALL] (that is, one ↑C), type (EDIT)[CALL].

	To suspend typeout, type [HOLD]; to resume typeout, type [HOLD]
		again.

The three characters β≡∨  are hidden under the  keys [CALL], [CLEAR],  and
[HOLD], respectively.  To get one of the characters β≡∨, you must quote it
by preceding  it  with  [NUL].   However, if  you  want  (META)  with  the
character, then  the  quoting is  automatic  with the  add-(META)  command
(EDIT)[NUL].   Thus  you  cannot  type  (META)[CALL],  (META)[CLEAR],   or
(META)[HOLD] because you would get (META)β, (META)≡, or (META)∨ instead.

You must tell the system you are a DM by either typing the TTY DM  command
or logging in with DM among your LOGIN options (if you have a DM with  the
full Stanford character set,  use the TTY DM128  command and DM128  option
instead).  The system will erase the DM  screen and then set the DM's  tab
stops while typing an initialization message at the top of the screen.  If
you have a DM terminal that lacks  hardware tabs (all of the AI Lab's  DMs
have them), then you should type TTY NO TABS (or have the NOTABS  option);
in that mode  each tab to  be output  will be converted  to an  equivalent
number of spaces, which will of course usually take longer to output  than
just a tab.

When you log  out, your terminal  will "go available"  about five  seconds
later.  A beep is output to  tell you when this has happened--your  screen
will not be erased at that time.   You should not hang up the phone  until
you hear this beep; otherwise, someone else may call in right then and  be
able to see  what was  displayed on your  screen.  When  your terminal  is
"available", you cannot  type [ESC] or  (META) until you  have typed  some
other character to initialize the terminal.  Typing [ESC] or (META) to  an
uninitialized terminal will  cause the  echoing of  a beep  with no  other
result.

If you  do  not get  the  initialization message  when  you first  type  a
character after  dialing in,  then you  should immediately  do a  [BREAK]P
(i.e., the three  characters [NUL] -  P) to force  it.  This will  usually
show you the  display screen  of the previous  user who  probably hung  up
before the terminal "went available".  If you don't type [BREAK]P in  this
case, there is no guarantee of consistent output as your terminal may have
its cursor at some  place other than  where the system  thinks it is.   If
[BREAK]P doesn't get  you the  initialization message but  does erase  and
redraw the screen, then type the monitor command TTY TABS (unless your  DM
terminal doesn't have hardware tabs), followed by another [BREAK]P,  which
should get you the message at the top of the screen.  If typeout screws up
after correct  initialization,  then  either you  are  having  phone  line
trouble or there is  a bug in  the DM display  service--the former is  the
best guess.  If you  get perfectly repeatable  typeout screwups, then  you
may have found a display service bug  and you should report to ME  exactly
what you did to cause it.  You should also verify that it happens on  more
than one phone  line.  If  it only  happens on  one phone  line, then  you
should report the phone line trouble to TED.


Notes:

The user job part of the wholine is now only updated when it has changed.

The don't-allow-beeps command [BREAK]B is not valid from DMs as they  have
no audio switch selection to preserve.  You can however turn your beeper's
volume up or down  on the back  of the keyboard.   Put your terminal  into
local mode by disabling  FULL DUPLEX and  type CTRL-G to  make it beep  to
adjust the volume.  Be sure to restore FULL DUPLEX when done.

Dpy programs (UPGIOT UUO) now run on DMs--see UUO.UPD[S,DOC], page 15.

While you are holding (even if HOLDING message does not appear), your line
editor will appear on the HOLDING message line (3rd line of screen).

Two new escape commands are now available to DM users for suppressing user
program display output  outside of  a specified  range of  columns on  the
display.  ESC m < (where m is decimal) suppresses all user display  output
to the left  of column  m, and  ESC n >  (n decimal)  suppresses all  user
display output to the right  of column m.  The  only type of output  these
commands affect is user program output generated by the UPGIOT UUO  (i.e.,
display program  output), and  even  then it  does  not affect  output  in
insert/delete mode nor does it affect output of CRs and LFs.

Note that ESC 5 < (for example) will suppress output to the left of column
5 and  therefore whatever  text already  appears in  columns 1  to 4  will
(normally) not be erased even when new text appears starting in column  5.
However, after an ESC 40 > (for example) old text in columns 41 to 80 will
usually be erased  by new  text at  or before  column 40  since output  of
actual text usually causes the rest of the line to be erased (except  when
this erase-to-end-of-line feature is  inhibited).  Also, if, for  example,
ESC 20 < and ESC 10 > are  given, all output is suppressed except for  CRs
and LFs and the line erases.

Thus these commands can be used to speed up displaying by E, WHO and other
display programs by suppressing unneeded output.

ESC < resets  the left DM  margin to zero  and ESC >  resets the right  DM
margin to infinity.  ESC N resets both margins, as does a RESET or  DPYCLR
UUO.  BRK > sets the right margin to 0, thus suppressing all text.
Use of DMs via TIPs


DM display  service is  now available  via TIPs.   It's most  useful  from
1200/150 baud ports (available on both SU-TIP and AMES-TIP) or faster, but
should work from 300 baud ports and other TIPs as well.

Some extra work, i.e., Step  (4) below, is required to  set up the TIP  to
allow EDIT key bits  and NULL characters through.   Here are the steps  to
follow (text to be typed in shown in brackets is optional):

(1) Dial up a TIP port.

(2) If you have dialed a nonhunting port (e.g., 1200/150 baud), reset  the
port to its standard configuration by typing

	@R[eset]<cr>

If you  have dialed  a hunting  port  (e.g., 110-300  baud), type  in  the
appropriate hunt  character (e.g.,  "E").  The  TIP should  type back  its
name, TIP software version number, and port number, e.g.,

	SU TIP 410 #: 10

[If the TIP  echoes "@R", but  doesn't print its  herald string, then  you
probably need to type

	@I[nsert] L[inefeed]<lf>

to allow TIP commands to be terminated with just a carriage return.]

(3)  Open a connection to SU-AI with

	@O[pen] 11<cr>

(4)  Next get into Eight-Bit Binary Mode by entering

	@B[inary] I[input] S[tart]<cr>

In this mode  all eight bits  of an  ASCII character are  sent through  to
SU-AI.  This feature  allows the  bit set  by the  EDIT key  and the  NULL
character generated by the NUL key to get through the TIP to SU-AI.   Note
that once this command is given no further TIP commands can be issued from
this port without hanging  up and redialing because  @ is sent on  through
also.

(5)  Finally tell SU-AI that you are a DM with either of

	.TTY DM<cr>
	.TTY Da[tamedia]<cr>

(6) Login and use the system as you normally would with a directly  dialed
DM.

(7) Logout as usual.

(8) Hit BREAK for a few seconds to break the connection.  Then hang up the
telephone.  This resets the TIP port, including the flushing of  Eight-Bit
Binary Mode.

In summary,  here is  the  normal sequence  of  commands you  should  type
between dialing up the TIP and logging in to SU-AI:

	@R	[or just "E" on a hunting port]
	@O 11
	@B I S
	.TTY DM

For more information  on the use  of TIPs,  see the "User's  Guide to  the
Terminal IMP" in TIPUG.BBN[UP,DOC].
Use of DMs from TENEX/TOPS20 Hosts


Date:  30 July 1977
Subject:  DM service from TENEX
From:  Geoff at SRI-KA (Geoffrey S. Goodfellow)

I have recently hacked up a version of NTELNET (a version of TELNET  which
uses the New Telnet protocol, now called TELNET at SRI and ISI) here (also
available at SUMEX-AIM) that DOES ALLOW you to use FULL Datamedia  display
service over  the net  from  Tenex to  SAIL.  All  one  must do  is  enter
TRANSPARENT MODE within  NTELNET (analogous  to Eight-Bit  Binary Mode  on
TIPs).  The only lossage right now is  that SAIL can only handle rates  of
1200 baud,  due to  special fillers  needed  for a  few functions  of  the
Datamedia; so far this is only provided for at 1200 baud, and as far as  I
am aware there is no way to set it for a higher baud rate.

If you use Datamedia display service at a higher speed, it is likely  that
you will lose when  inserting lines or  the like on  the screen.  You  can
usually manage at 2400 baud, but anything higher is near disaster.
Use of DMs from ITS Hosts


People who wish to use DMs on ITS should first declare their terminal type
to ITS via

	:tctyp Datamedia

If using a baud  rate greater than  1200, the user  should also include  a
PADCR value of 1 to 4 as necessary for the user's baud rate.

All of the ITS display facilities are  now available to the user.  A  user
can then use ITS user TELNET's DM simulator to connect to SU-AI.  The most
straightforward way of doing this  is to run TELNET  as SA or SAIL,  which
will set TELNET  up in  magic mode automatically,  saving the  user a  few
commands that otherwise would be  necessary (including telling SU-AI  that
you are a DM!).

There is no way currently to get EDIT sent down to SU-AI, as there are  no
real DMs locally  at Cambridge  where this can  be tested  at the  present
time.

A very  desirable alternative  is to  use one  of the  TVs there.   TELNET
checks to  see if  the terminal  has a  bucky bit  keyboard and  the  SAIL
graphics set in addition to insert/delete mode (these are options not  all
ITS displays may have; i/d  mode is required to use  any of the TELNET  DM
stuff), and if the terminal fits all of these requirements, TELNET  enters
a special mode in which all the TV keys are mapped into their DM bucky bit
protocol equivalents.  ITS ↔ SU-AI  mappings are done invisibly such  that
the Knight keyboard appears  to be a funny  Stanford keyboard.  Thus,  the
user at an ITS TV can be, more or less, a SU-AI TV.